Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-253888 | JUEX-NM-000110 | SV-253888r879561_rule | Medium |
Description |
---|
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). |
STIG | Date |
---|---|
Juniper EX Series Switches Network Device Management Security Technical Implementation Guide | 2023-03-23 |
Check Text ( C-57340r843695_chk ) |
---|
Determine if the network device generates audit records for executed commands. Verify the system logs the facility "any", or minimally "change-log" and "interactive-commands", and the logging level is appropriate. Generally, the "all" (debug) logging level should be avoided because the number of logged messages is significant. [edit system syslog] host any info; } file change-log info; interactive-commands info; } Note: If minimally logging only configuration changes, there will be other files receiving the events from the other logging facilities (for example "authorizations" or "firewall"). Syslog outputs in standard format unless the "structured-data" directive is configured. Verify the "structured-data" command for all files and external syslog servers requiring that format. For example: [edit system syslog] host change-log info; interactive-commands info; structured-data; } file any info; structured-data; } If the network device does not generate audit records for executed commands, this is a finding. |
Fix Text (F-57291r843696_fix) |
---|
Configure the network device to generate audit records for executed commands. set system syslog host set system syslog host -or- set system syslog host set system syslog file set system syslog file -or- set system syslog file |